[CI/CD] Improve assertion doc generation#1400
Merged
sean-breen merged 49 commits intomainfrom Nov 26, 2025
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1400 +/- ##
=======================================
Coverage 86.27% 86.27%
=======================================
Files 102 102
Lines 12622 12622
=======================================
Hits 10890 10890
Misses 1253 1253
Partials 479 479 Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
sean-breen
changed the title
dhurley
approved these changes
Nov 21, 2025
craigell
approved these changes
Nov 25, 2025
Akshay2191
pushed a commit
that referenced
this pull request
Dec 18, 2025
* reduce packaging time by building only two binaries * use pushd * tidy up console output * perform string substitution when creating files for release packaging * remove docker build for FreeBSD packager * perform string sub on architecture var * update make target * [skip ci] clean up log output * add assertion step to release-branch, sha checksum and build times * archive the binaries for generating assertion doc * remove matrix from step * fix ref * use a relative path for reusable action * add package version to call * remove secrets * [skip ci] swap runner for test * [skip ci] fix flow * [skip ci] fix flow * update actions versions for artifacts * [skip ci] more log output when archiving binaries * [skip ci] run from this branch for test * [skip ci] run from this branch for test * [skip ci] run from this branch for test * [skip ci] add back gpg key gen * [skip ci] fix tarball path, use cd instead of popd * [skip ci] move assertion doc gen into release-branch.yml * [skip ci] install go for assertion doc job * [skip ci] use go mod download * [skip ci] * [skip ci] * [skip ci] add artifactory creds * make assertion optional * call reusable assertion workflow * [skip ci] fix perms * [skip ci] fix perms * [skip ci] allow run via dispatch, artifact id as input * [skip ci] add run id for downloading artifacts * [skip ci] list artifacts and download by name * make run id required * remove ref from checkout, use current commit or default branch * ensure checkout uses inputs.releaseBranch in release branch workflow * use self-hosted runner for build
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Adds the assertion document generation as an option when running the release branch workflow.
For the assertion doc, we need to generate a few extra files to pass along, mainly:
These get stored in files alongside the binary which is created in
make package, and these files along with the binary itself are stored to GitHub artifacts.When 'Store assertion document' option is selected:
When running the Assertion doc workflow manually:
Run IDof the pipeline which created the build artifacts, if they are still in GitHub the workflow will download these, and proceed with the workflow as normal.Checklist
Before creating a PR, run through this checklist and mark each as complete.
CONTRIBUTINGdocumentmake install-toolsand have attached any dependency changes to this pull requestREADME.md)